Setting Up an HTTPS Connection
Protege controllers come preconfigured with a self-signed certificate and HTTPS enabled by default, so that communications between the controller and the web browser are always encrypted. However, an alternative certificate can be installed if preferred. Installing a third-party certificate on the controller will remove the security warning which you may see in your browser when accessing a controller with a factory certificate.
For older controllers without a default HTTPS certificate, it may be possible to install an HTTPS certificate after upgrading the controller's operating system. This is strongly recommended for any controller that is connected to internal or external networks via a router. Contact ICT Technical Support for more information.
Two different connection methods are available, each of which can be configured directly within the web interface:
- Validating and installing a third-party certificate obtained from a certificate authority.
- Installing a self-signed certificate (recommended for testing only).
If the controller is factory defaulted, any user-created HTTPS certificates are removed and the default certificate is reloaded. Custom certificates will need to be reinstalled.
For configuration and version requirements refer to AN-280 HTTPS Connection to the Protege WX Controller